Fix long task timer implementation #1674
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The implementation of
CumulativeHistogramLongTaskTimer
in micrometer has a known issue. Besides, the implementation ofwriteLongTaskTimer
is not compatible withCumulativeHistogramLongTaskTimer
and results in non-sense histogram. The +Inf bucket should be the total counts of elements in the histogram, but it's set to the active count.teletraan/deploy-service/universal/src/main/java/com/pinterest/teletraan/universal/metrics/micrometer/PinStatsPublisher.java
Lines 213 to 228 in cddbb72
Because PinStats supports GaugeHistogram, this PR adopts the second recommendation in the micrometer issue.
GaugeHistogram works for Teletraan's use case because the purpose of this metrics is to allow users to detect out of SLA host launches immediately. It's not intended to provide the histogram of actual host launch durations.
The fix is simply to inherit from
DefaultLongTaskTimer
instead ofCumulativeHistogramLongTaskTimer
.